A scope is a means for partitioning data within a single AssetWise community. Each scope may have its own set of classes, attributes, templates, organizations, and people. Certain list values (for example, Responsibilities) may also be unique to a scope.

Scope names within a community must be unique. Users, via their assignments to roles, have rights to access data in some scopes but not in others.

As part of the installation of a community, a default scope, named Global, is created. Additional scopes are only necessary if there is a requirement to create and maintain data in the same community that may exist independently of other data. Examples where this may be applicable are project-based data and organizational data.

A scope may be in hierarchical structure, for example, where there is a program that is made up of many smaller projects. The program would be the parent scope, and each project would be a child of this parent scope.

Users can view and use data from the Global scope, as well as from any scope associated with a role to which they belong, and any other parent scope. To be able to access a scope, the user must belong to at least one role in each scope in the hierarchy.

The scope utility is available on every AssetWise page, on the right side of the Navigation bar.

When you select Scope, you can view all visible scopes and change the current scope. For example: